System and method for session restoration after node failure

ABSTRACT

A system and method for restoring a session state of a client device has been provided. The system comprises a memory with instructions executable by a processor to receive a first request from the client device, where the first request is a first type of request and is associated with a new session of the client device; process the first request without persisting a session state of the new session in the database node; receive a second request from the client device, where the second request is a first instance of a second type of request and is associated with the new session; and in response to determining to restore a persisted session state, restore the persisted session state for the client device from the database node, and assign the persisted session state as the session state of the new session of the client device.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This is a continuation application of U.S. patent application Ser. No.15/484,885, filed Apr. 11, 2017, which claims the benefit of U.S.Provisional Application No. 62/325,787, filed Apr. 21, 2016, the entirecontents of which are hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure is generally related to session restoration afternode failure.

BACKGROUND

A client and a web server can communicate over stateless protocols suchas HTTP. Client-server interactions can be carried out over a series ofrelated client requests and server responses. A web application cancreate a session for a client to maintain session state betweenrequests. A session can start with the first request that the clientmakes to the server and can end when the client disconnects or thesession times out. To track the state of the client-server interactions,a client can be assigned a session identifier and a session stateassociated with the session identifier can be maintained on the server.Session state can be application specific and include informationrelating to components, contexts, user interface elements, data andparameters related to a current state of a client-server interaction.The session state may also be saved to a database to enable, e.g.,recovery upon server interruption.

SUMMARY

Disclosed herein are aspects of systems and methods for sessionrestoration after application node failure.

In an implementation, a system for restoring session state of a clientdevice is provided. The system includes database node configured topersist at least a portion of the session state, and a first applicationnode having a processor and a memory. The memory includes instructionsexecutable by the processor to receive a first request from the clientdevice that is a first type of request and is associated with a newsession of the client device, process the first request withoutpersisting a session state of the new session in the database node, andreceive a second request from the client device that is associated withthe new session and is a first instance of a second type of requestreceived by the first application node in the context of the newsession. The memory further includes instructions to, in response todetermining to restore a persisted session state, to restore thepersisted session state from the database node and assign the persistedsession state as the session state of the new session of the clientdevice.

In another implementation, a method for a restoring session state inresponse to a category of a request received from a client device isprovided. The method includes receiving, at a first application node, afirst request from the client device, where the first request is a firsttype of request and is associated with a new session of the clientdevice. The method further includes processing, by the first applicationnode, the first request without persisting a session state of the newsession in a database node; receiving, at the first application node, asecond request from the client device, where the second request is afirst instance of a second type of request and is associated with thenew session, restoring, by the first application node, a persistedsession state from the database node, and assigning, by the firstapplication node, the persisted session state as the session state ofthe new session of the client device.

In another implementation, a non-transitory computer-readable storagemedium is provided. The non-transitory computer-readable storage mediumincludes executable instructions that, when executed by a processor,facilitates performance of operations for restoring a session state inresponse to a category of a request received from a client device. Theinstructions include receiving, at a first application node, a firstrequest from the client device that is a first type of request and isassociated with a new session of the client device. The instructionsfurther include processing, by the first application node, the firstrequest without persisting a session state of the new session in adatabase node; receiving, at the first application node, a secondrequest from the client device that is a first instance of a second typeof request and is associated with the new session, and in response todetermining to restore a persisted session state, restoring, by thefirst application node, the persisted session state from the databasenode, and assigning, by the first application node, the persistedsession state as the session state of the new session of the clientdevice.

These and other aspects of this disclosure are disclosed in thefollowing detailed description, the appended claims, and theaccompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The description herein makes reference to the accompanying drawingswherein like reference numerals refer to like parts throughout theseveral views.

FIG. 1 is a block diagram of an example of an electronic computing andcommunications system.

FIG. 2 is a block diagram of an example internal configuration of acomputing device of an electronic computing and communications system.

FIG. 3 is a block diagram of an example of a session restoration system.

FIG. 4 is an example of a data structure usable for session restoration.

FIG. 5 is a flowchart illustrating an example of a technique for sessionrestoration.

FIG. 6 is a flowchart illustrating an example of another technique forsession restoration.

DETAILED DESCRIPTION

A client and/or application node(s) can be configured such that theclient can send stateful and stateless requests in the same session. Asession is a series of request-responses between a requester, such as aclient, and a receiver, such as a server. A stateful request can be of atype that is intended to use and/or update the session state of asession. A stateless request can be of a type that is not intended touse and/or update the session state. For example, an API request, suchas one using a representational state transfer (REST) protocol can beconsidered a stateless request and a UI request, such as one triggeredby a user, can be considered a stateful request.

After receiving a request from a client, an application node can createa session for the client. The session can include a session id thatidentifies the session and a session state that includes informationrelating to the session. The session state can be referred to during theprocessing of future requests from the client. The session id can bemaintained by the client in a cookie or other storage mechanism (suchas, for example, HTML5 storage). The application node can maintain thesession id and session state in memory for the duration of the session.To permit failover in the event of an application node failure, theapplication node can persist the session state in a permanent store,such as a database operating on a database node. The client can beassociated with the persisted session state such as by maintaining areference to the persisted session state in a cookie or other storagemechanism. The application node can persist and/or update the sessionstate in response to stateful requests and not in response to statelessrequests. The application node can be configured to not restore thesession state in response to a stateless request.

Thus, in the disclosed implementations, a client can send a request to afirst application node, the first application node can create andmaintain a session for that client, and the first application node canpersist the session for that client. The client can maintain the sessionid associated with the session and a reference to the persisted session.The client can make additional requests to the first application nodewith the session id so that the first application node can respond tosuch requests using the maintained session state. After a failure of thefirst application node, requests from the client node may be redirected,such as by a load balancer, to a second application node or any other ofa plurality of application nodes. Alternatively, requests from theclient node may be directed to the first application node after waitingfor a predetermined time period to enable the first application node torecover from the failure or once the first application node has beendetected to have recovered from the failure. After failure, the firstapplication node no longer has the session state maintained.

In an implementation where stateless and stateful requests are treateddifferently, the process of restoration of session state can be adjustedto take into account the type of request. For example, if a firstrequest received by an application node after a failure is a statefulrequest, the application node can be configured to create a new sessionand restore the session state from the prior session (that occurredbefore the failure) to the new session using the reference to thepreviously persisted session maintained by the client. The new sessionand corresponding newly restored session state can then be persistedusing the database node. The client can then be provided with thesession id for the new session and an updated reference to a newlypersisted session state.

A problem arises when a first request received by an application nodeafter a failure is a stateless request. Restoring the session stateafter receiving the first request that is a stateless request from theclient may lead to inconsistent results. If a session state forstateless requests is not maintained and/or persisted, a restoredsession state may become unavailable to later requests or a laterrestoration of session state may result in an inconsistent sessionstate.

For further clarification on the problem, consider the following examplewhere a user fills an online form through a web browser. The online formis comprised of four different steps and the user proceeds through thesteps by pressing a “next” button. When the user presses “next,” theinput data of the user is transported to a server and saved in a sessionstate for the user. At the same time that the user fills out the onlineform, the user's web browser issues background stateless messages to theserver. The server fails before the user presses the “next” buttonassociated and the user's web browser issues a background statelessrequest before the third step is submitted as well. A load balancer thendetects the server failure and forwards the browser's background requestto a second server. This being the first request received by the secondserver, a component of the second server may, even though not necessaryas the request is a stateless request and a stateless request bydefinition does not use and/or maintain a session state, create a secondsession state for the user. When the user presses “next” aftercompleting the third step, the second server receives the request. Asthe second session state is already associated with the user, the secondserver uses the second session state in the processing of the dataassociated with the third step. However, this results in data loss asthe input data from the first two steps are no longer part of the user'ssecond session state.

To address such a problem, the present disclosure includes anapplication node that can include a session restoration system whichcategorizes requests received from a client to determine when a firststateful request is received from a client. As such, the client'ssession state is restored only after receiving the first statefulrequest even if one or more prior requests were stateless requests andthus created a new session on the application node. Such a sessionrestoration system can be configured so that the session state is notrestored after receiving the one or more prior stateless requests. Assuch, a session state can be maintained for a client's stateful requestsafter a failure while avoiding the inconsistencies or errors that arecaused by restoring sessions states after receiving interspersedstateless requests.

Implementations of the present disclosure provide technologicalimprovements particularly to computer networks, for example, thoseconcerning client session restoration. Computer network-specifictechnological problems, such as loss of session state information, canbe wholly or partially solved by implementations of the presentdisclosure. For example, the present disclosure enables the properrestoration of a session state after a new session is established basedon a received stateless request. Implementations of the presentdisclosure can thus introduce new and efficient improvements in the waysin which a client session state is restored by categorizing requestsinto stateful and stateless and only restoring the session state once astateful request is received thereby ignoring potential restoration whenonly stateless requests are received.

To describe some implementations in greater detail, reference is firstmade to examples of hardware structures. FIG. 1 is a block diagram of anexample of an electronic computing and communications system 100. Asused herein, the term “electronic computing and communications system,”or variations thereof, can be, or include, a distributed computingsystem (e.g., a client-server computing system), a cloud computingsystem, a clustered computing system, or the like.

The system 100 can include one or more customers 102, which may be apublic entity, private entity, or other corporate entity or individualthat purchases or otherwise uses services of a software provider, suchas a PaaS service provider. The customer 102 can include one or moreclients. For example, and without limitation, the customer 102 caninclude a client 104. The client 104 can comprise a computing system,which can include one or more computing devices, such as a mobile phone,a tablet computer, a laptop computer, a notebook computer, a desktopcomputer, or any other suitable computing device or combination ofcomputing devices. In some implementations, the client 104 can beimplemented as a single physical unit or as a combination of physicalunits. In some implementations, a single physical unit can includemultiple clients.

The client 104 can be an instance of software running on a customerdevice associated with the customer 102. As used herein, the term“software” can include, but is not limited to, applications, programs,instances, processes, threads, services, plugins, patches, applicationversion upgrades, or any other identifiable computing aspect capable ofaccessing or interacting with, directly or indirectly, a database. Thesystem 100 can include any number of customers or clients or can have aconfiguration of customers or clients different from that generallyillustrated in FIG. 1. For example, and without limitation, the system100 can include hundreds or thousands of customers, and at least some ofthe customers can include or be associated with any number of clients. Acustomer can include a customer network or domain. For example, andwithout limitation, the client 104 can be associated or communicate witha customer network or domain.

The system 100 can include a datacenter 108. The datacenter 108 caninclude one or more servers. For example, and without limitation, thedatacenter 108, as generally illustrated, includes an application server112 and a database server 116. A datacenter, such as the datacenter 108,can represent a geographic location, which can include a facility, wherethe one or more servers are located. The system 100 can include anynumber of datacenters and servers or can include a configuration ofdatacenters and servers different from that generally illustrated inFIG. 1. For example, and without limitation, the system 100 can includetens of datacenters, and at least some of the datacenters can includehundreds or any suitable number of servers. In some implementations, thedatacenter 108 can be associated or communicate with one or moredatacenter networks or domains, which can include domains other than theclient domain.

The client 104 and the servers associated with the datacenter 108 may beconfigured to connect to, or communicate via, a network 106.Furthermore,a client 104 associated with the customer 102 can connect to the network106 via a communal connection point, link, or path, or using a distinctconnection point, link, or path. A connection point, link, or path canbe wired, wireless, use other communications technologies, or acombination thereof.

The network 106 can include, for example, the Internet and/or thenetwork 106 can be, or include, a local area network (LAN), a wide areanetwork (WAN), a virtual private network (VPN), or any other public orprivate means of electronic computer communication capable oftransferring data between a client, such as the client 104, and one ormore servers associated with the datacenter 108, or a combinationthereof. The network 106, the datacenter 108, or any other element, orcombination of elements, of the system 100 can include network hardwaresuch as routers, switches, load balancers, other network devices, orcombinations thereof. For example, the datacenter 108 can include a loadbalancer 110 for routing traffic from the network 106 to various serversassociated with the datacenter 108.

The load balancer 110 can route, or direct, computing communicationstraffic, such as signals or messages, to respective elements of thedatacenter 108. For example, the load balancer 110 can operate as aproxy, or reverse proxy, for a service, such as an Internet-deliveredservice, provided by the datacenter 108 to one or more remote clients,such as the client 104, via the network 106. Routing functions of theload balancer 110 can be configured directly or via a Domain Name System(DNS). The load balancer 110 can coordinate requests from remoteclients, such as the client 104, and can simplify client access bymasking the internal configuration of the datacenter 108 from the remoteclients. Request coordination can include maintaining information forsessions, such as sticky sessions, between a client and a service orsoftware provided by the datacenter 108.

Maintaining information for a sticky session can include maintaininginformation to forward requests associated with a session from a clientto an identified element of the datacenter 108 for the session. A loadbalancer 110 can operate as a firewall, allowing or preventingcommunications based on configuration settings. Although the loadbalancer 110 is depicted in FIG. 1 as being within the datacenter 108,in some implementations, the load balancer 110 can instead be locatedoutside of the datacenter 108, for example, when providing globalrouting for multiple datacenters. In some implementations, loadbalancers can be included both within and outside of the datacenter 108.

The datacenter 108 may include an application server 112 and a databaseserver 116. The application server 112 or the database server 116 can bea computing system, which can include one or more computing devices,such as a desktop computer, a server computer, or any other computercapable of operating as a server. In some implementations, theapplication server 112 or the database server 116 can be non-hardwareservers implemented on a physical device, such as a hardware server. Insome implementations, the application server 112 and the database server116 can be implemented as a single hardware server or as a singlenon-hardware server implemented on a single hardware server. Of course,any number of application servers or database servers can be implementedat the datacenter 108, and the datacenter 108 can include servers otherthan or in addition to the application server 112 or the database server116.

In some implementations, the application server 112 includes anapplication node 114, which can be a process executed on the applicationserver 112. For example, and without limitation, the application node114 can be executed in order to deliver services to a client, such asthe client 104, as part of web application software. The applicationnode 114 can be implemented using processing threads, virtual machineinstantiations, or other computing features of the application server112. In some implementations, the application node 114 can store,evaluate, or retrieve data from a database, such as the database 118 ofthe database server 116.

The application server 112 can include any suitable number ofapplication nodes, depending upon a system load or other characteristicsassociated with the application server 112. For example, and withoutlimitation, the application server 112 can include two or more nodesforming a node cluster. In some implementations, the application nodesimplemented on a single application server 112 can run on differenthardware servers.

The database server 116 can be configured to store, manage, or otherwiseprovide data for delivering services to the client 104 over a network.The database server 116 may include a data storage unit, such as adatabase 118, which can be accessible by software executed on theapplication node 114. The database 118 may be implemented as arelational database management system (RDBMS), an object database, anXML database, a configuration management database (CMDB), a managementinformation base (MIB), one or more flat files, other suitablenon-transient storage mechanisms, or a combination thereof. By way ofnon-limiting example, the system 100, in some implementations, caninclude an XML database and a CMDB. While limited examples aredescribed, the database 118 can be configured as or comprise anysuitable database type. Further, the system 100 can include one, two,three, or any suitable number of databases configured as or comprisingany suitable database type or combination thereof.

In some implementations, the database 118 can be configured as orcomprise a CMDB. A CMDB can comprise a plurality of configuration items(CIs), attributes associated with the CIs, or relationships between theCIs. A CI can be a CMDB record that represents an infrastructure entity,device, or units of the system 100. For example, the customer 102, theclient 104, the network 106, the datacenter 108, the load balancer 110,the application server 112, the application node 114, the databaseserver 116, the database 118, or any other element, portion of anelement, or combination of elements of the electronic computing andcommunications system 100 can be represented in the CMDB by a CI.

The CMDB can include information describing the configuration, the role,or both the configuration and the role, of an element of the system 100.In some implementations, an MIB can include one or more databaseslisting characteristics of the elements of the system 100. In someimplementations, an object identifier (OID) can represent objectidentifiers of objects or elements in the MIB.

One or more databases (e.g., the database 118), tables, other suitableinformation sources, or portions or combinations thereof may be stored,managed, or otherwise provided by one or more of the elements of thesystem 100 other than the database server 116, such as the client 104 orthe application server 112.

Some or all of the systems and techniques described herein can operateor be executed on or by the servers associated with the system 100. Forexample, restoring a session state of a client device can be implementedby application node 114. In some implementations, the systems andtechniques described herein, portions thereof, or combinations thereofcan be implemented on a single device, such as a single server, or acombination of devices, for example, a combination of the client 104,the application server 112, and the database server 116.

In some implementations, the system 100 can include devices other thanthe client 104, the load balancer 110, the application server 112, andthe database server 116 as generally illustrated in FIG. 1. In someimplementations, one or more additional servers can operate as anelectronic computing and communications system infrastructure control,from which servers, clients, or both servers and clients, can bemonitored, controlled, configured, or a combination thereof.

The network 106, one or more datacenters, such as the datacenter 108,and one or more load balancers, such as the load balancer 110, may beimplemented within a distributed computing system. A load balancerassociated with a distributed computing system (e.g., the load balancer110) can communicate with the network 106, one or more datacenters(e.g., the datacenter 108), other load balancers, or a combinationthereof. The load balancer 110 can be configured to route communicationsto a primary datacenter, identify a failover condition (e.g., anenumerated failover condition) at the primary datacenter, and redirectcommunications to a secondary datacenter until the failover condition isresolved. Although illustrated as a single unit in FIG. 1, a loadbalancer 110 can be implemented as multiple physical or logical units.For example, a distributed computing system can include distinct routingunits, load balancing units, firewall units, or the like.

The primary datacenter can include a primary database, such as thedatabase 118, and the secondary datacenter can include a secondarydatabase. The secondary database can include an exact or substantiallyexact mirror, copy, or replication of the primary database. The primarydatabase or the secondary database can be implemented as an RDBMS, anobject database, an XML database, one or more flat files, or the like.

An application node implemented within a distributed computingenvironment can connect to or communicate with the primary database,which can be associated with the datacenter with which the applicationnode is associated, or associated with another datacenter. For example,a primary datacenter can include a primary database and a first set ofapplication nodes. A secondary datacenter can include a secondarydatabase and a second set of application nodes. The application nodes ofthe first and second sets can provide a software service to remoteclients, and can read or write data in the primary database. Thesecondary database can mirror changes made to the primary database andprevent write operations from being performed directly on the secondarydatabase. In the event that a failover condition associated with theprimary database is identified, the secondary database can operate asthe primary database and can allow read or write access to data. Theprimary database can then operate as the secondary database, mirror thenew primary database, and prevent direct write access to the newsecondary database.

A distributed computing system can allocate resources of a computernetwork using a multi-tenant or single-tenant architecture, for example.Allocating resources in a multi-tenant architecture can includeinstallations or instantiations of one or more servers, such asapplication servers, database servers, or any other server, orcombination of servers, that can be shared amongst multiple customers.For example, a web server, such as a unitary Apache installation; anapplication server, such as a unitary Java Virtual Machine; or a singledatabase server catalog, such as a unitary MySQL catalog, can handlerequests from multiple customers. In some implementations of amulti-tenant architecture, the application server, the database server,or both can distinguish between and segregate data or other informationof the various customers using the system.

In a single-tenant infrastructure (which can also be referred to as amulti-instance architecture), separate web servers, application servers,database servers, or combinations thereof can be provisioned for atleast some customers or customer sub-units. Customers or customersub-units can access one or more dedicated web servers, havetransactions processed using one or more dedicated application servers,or have data stored in one or more dedicated database servers, catalogs,or both. Physical hardware servers can be shared such that multipleinstallations or instantiations of web servers, application servers,database servers, or combinations thereof can be installed on the samephysical server. An installation can be allocated a portion of thephysical server resources, such as RAM, storage, communicationsbandwidth, or processor cycles.

A customer instance can include multiple web server instances, multipleapplication server instances, multiple database server instances, or acombination thereof. The server instances can be physically located ondifferent physical servers and can share resources of the differentphysical servers with other server instances associated with othercustomer instances. In a distributed computing system, multiple customerinstances can be used concurrently. Other configurations orimplementations of customer instances can also be used. The use ofcustomer instances in a single-tenant architecture can provide, forexample, true data isolation from other customer instances, advancedhigh availability to permit continued access to customer instances inthe event of a failure, flexible upgrade schedules, an increased abilityto customize the customer instance, or a combination thereof.

FIG. 2 is a block diagram of an example of an internal configuration ofa computing device 200 of an electronic computing and communicationssystem, such as a client 104 or a server, such as an application server112 or a database server 116, of the system 100 shown in FIG. 1. Aspreviously described, a client or server can be a computing systemincluding multiple computing devices or a single computing device, suchas a mobile phone, a tablet computer, a laptop computer, a notebookcomputer, a desktop computer, a server computer, or other suitablecomputing devices.

A computing device 200 can include components or units, such as aprocessor 202, a bus 204, a memory 206, peripherals 214, a power source216, a network communication unit 218, a user interface 220, othersuitable components, or a combination thereof.

The processor 202 can be a central processing unit (CPU), such as amicroprocessor, and can include single or multiple processors havingsingle or multiple processing cores. Alternatively, the processor 202can include another type of device, or multiple devices, now existing orhereafter developed, capable of manipulating or processing information.For example, the processor 202 can include multiple processorsinterconnected in any manner, including hardwired or networked,including wirelessly networked. In some implementations, the operationsof the processor 202 can be distributed across multiple physical devicesor units that can be coupled directly or across a local area or othersuitable type of network. In some implementations, the processor 202 caninclude a cache, or cache memory, for local storage of operating data orinstructions.

The memory 206 can include volatile memory, non-volatile memory, or acombination thereof. For example, the memory 206 can include volatilememory, such as one or more DRAM modules such as DDR SDRAM, andnon-volatile memory, such as a disk drive, a solid state drive, flashmemory, Phase-Change Memory (PCM), or any form of non-volatile memorycapable of persistent electronic information storage, such as in theabsence of an active power supply. The memory 206 can include anothertype of device, or multiple devices, now existing or hereafterdeveloped, capable of storing data or instructions for processing by theprocessor 202. The processor 202 can access or manipulate data in thememory 206 via the bus 204.

Although shown as a single block in FIG. 2, the memory 206 can beimplemented as multiple units. For example, a computing device 200 caninclude volatile memory, such as RAM, and persistent memory, such as ahard drive or other storage. The memory 206 can be distributed acrossmultiple clients or servers, such as network-based memory or memory inmultiple clients or servers performing the operations of clients orservers.

The memory 206 can include executable instructions 208, data, such asapplication data 210, an operating system 212, or a combination thereof,for immediate access by the processor 202. The executable instructions208 can include, for example, one or more application programs, whichcan be loaded or copied, in whole or in part, from non-volatile memoryto volatile memory to be executed by the processor 202. The executableinstructions 208 can be organized into programmable modules oralgorithms, functional programs, codes, code segments, or combinationsthereof to perform various functions described herein. For example, theexecutable instructions 208 can include instructions to restore sessionstate of a client device.

The application data 210 can include, for example, user files, databasecatalogs or dictionaries, configuration information or functionalprograms, such as a web browser, a web server, a database server, or acombination thereof. The operating system 212 can be, for example,Microsoft Windows®, Mac OS X®, or Linux®, an operating system for asmall device, such as a smartphone or tablet device; or an operatingsystem for a large device, such as a mainframe computer. The memory 206can comprise one or more devices and can utilize one or more types ofstorage, such as solid state or magnetic storage.

The peripherals 214 can be coupled to the processor 202 via the bus 204.The peripherals can be sensors or detectors, or devices containing anynumber of sensors or detectors, which can monitor the computing device200 itself or the environment around the computing device 200. Forexample, a computing device 200 can contain a geospatial locationidentification unit, such as a global positioning system (GPS) locationunit. As another example, a computing device 200 can contain atemperature sensor for measuring temperatures of components of thecomputing device 200, such as the processor 202. Other sensors ordetectors can be used with the computing device 200, as can becontemplated. In some implementations, the power source 216 can be abattery, and the computing device 200 can operate independently of anexternal power distribution system. Any of the components of thecomputing device 200, such as the peripherals 214 or the power source216, can communicate with the processor 202 via the bus 204. In someimplementations, a client or server can omit the peripherals 214.

The network communication unit 218 can also be coupled to the processor202 via the bus 204. In some implementations, the network communicationunit 218 can comprise one or more transceivers. The networkcommunication unit 218 can, for example, provide a connection or link toa network, such as the network 106, via a network interface, which canbe a wired network interface, such as Ethernet, or a wireless networkinterface. For example, the computing device 200 can communicate withother devices via the network communication unit 218 and the networkinterface using one or more network protocols, such as Ethernet, TCP,IP, power line communication (PLC), WiFi, infrared, GPRS, GSM, CDMA, orother suitable protocols.

A user interface 220 can include a display; a positional input device,such as a mouse, touchpad, touchscreen, or the like; a keyboard; orother suitable human or machine interface devices. The user interface220 can be coupled to the processor 202 via the bus 204. Other interfacedevices that permit a user to program or otherwise use the computingdevice 200 can be provided in addition to or as an alternative to adisplay. In some implementations, the user interface 220 can include adisplay, which can be a liquid crystal display (LCD), a cathode-ray tube(CRT), a light emitting diode (LED) display (e.g., an OLED display), orother suitable display.

FIG. 3 is a block diagram of an example of a session restoration system300 for session restoration. The session restoration system 300 can beimplemented by a computing device, such as the computing device 200 ofFIG. 2. The session restoration system 300 can be implemented by anapplication node, such as the application node 114 of FIG. 1. Thesession restoration system 300 includes a session restoration module 302and a request categorizer module 304.

The session restoration module 302 can update a session state of aclient, such as client 104 of FIG. 1 and a session state in a database,such as database 118 of FIG. 1. The session restoration system 300 canrestore the client's session state from the database. The sessionrestoration module 302 can update and restore a session state inaccordance with the sample steps/operations provided below in FIG. 5.

The request categorizer module 304 can determine a category of a clientrequest. For example, the request categorizer module 304 can determine arequest is a stateful request or a stateless request. The requestcategorizer module 304 can examine the request to determine if itscharacteristics match that of a stateful request or a stateless request.The request categorizer module 304 can determine that a request is astateless request if the request is, for example, an API request such asa SOAP or REST request. The request categorizer module 304 can determinethat a request is stateless when any of the following occur includingbut not limited to determining that a request is automatically submittedwithout user intervention or interaction, based on a lookup againstknown characteristics, based on a parameter of the request, based onstored information, and a combination thereof. A request automaticallysubmitted without user intervention or interaction can be a requestsubmitted by a script executing in a web browser of a client device,such as the client 104 of FIG. 1. The script can, for example,automatically submit AJAX requests to an application node. The requestcategorizer module 304 can store, for later retrieval, the determinedcategory of a client request.

In an implementation, the session restoration module 302, the requestcategorizer module 304, or both may be implemented outside theapplication node 114 of FIG. 1 and provide a session transfer service tothe application node 114 of FIG. 1.

FIG. 4 is an example of a data structure 400 usable for sessionrestoration. Implementations of the data structure 400 can be used, forexample, to maintain a session state on an application node or topersist a session state in a permanent store such as the database 118 ofFIG. 1. The data structure 400 can include records such as entry 410which can include information about the session state of a particularclient. Specifically, the entry 410 includes a client identificationnumber (ID) 402, a session state 404, a last updated timestamp 406, anda session ID 408. The client ID 402 is a unique identifier of a clientdevice, such as the client 104 of FIG. 1. The client ID 402 can includebut is not limited to an IP address, a MAC address, and/or an identifierstored by a client in a cookie or other storage mechanism.

The session state 404 can be configured to store at least a subset of asession state maintained by an application node, such as the applicationnode 114 of FIG. 1. The session state 404 can be configured to permitdata to be saved in any number of formats including, without limitation,a string, an XML blob, name-value pairs, a serialized object, and anencoded string.

The last updated timestamp 406 indicates when the information for arecord was, for example, created or last updated. In another embodiment,the data structure 400 includes both a created timestamp that denoteswhen the record was created and a last updated timestamp that denoteswhen the record was last updated (if at all). The value of the lastupdated timestamp 406 can be, for example, automatically set by thepermanent store system or by the session restoration system 300. Thesession ID 408 can be the session ID of a session that is persisted inthe data structure 400. The session ID 408 can be generated by, forexample, an application node when a first request from a client isreceived by the application node. Alternatively, the session ID 408 canbe assigned by another device or module, such as a load balancer.

The data structure 400 can have different data elements than those shownin FIG. 4. The data structure 400 can have additional data elements,omit data elements, or modify data elements 402-408. For example, asingle data element for identification may be used instead of usingseparate data elements as the client ID 402 and the session ID 408. Inthis example, either the client ID 402 or the session ID 408 can beomitted.

FIG. 5 is a flowchart illustrating an example of a technique 500 forsession restoration. The technique 500 is implemented by a sessionrestoration module (similar to the session restoration module 302 ofFIG. 3). The technique 500 can be executed using computing devices, suchas the systems, modules, and devices described with respect to FIGS.1-4. The technique 500 can be performed, for example, by executing amachine-readable program or other computer-executable instructions, suchas instructions or programs described according to JavaScript, C, orother such instructions. The steps, or operations, of the technique 500or any other technique, method, process, or algorithm described inconnection with the implementations disclosed herein can be implementeddirectly in hardware, firmware, software executed by hardware,circuitry, or a combination thereof.

At operation 502, the application node 114 of FIG. 1 receives a firstrequest from the client 104 of FIG. 1. A new session is generated inresponse to the request. The new session can include a new session IDand a persisted session state (similar to the session ID 408 and thesession state 404 of FIG. 4). The new session may be generated by anapplication node, such as the application node 114 of FIG. 1 dependingon the implementation. At operation 504, a session restoration moduledetermines whether a persisted session state associated with the client104 should be restored from the data structure 400. The sessionrestoration module may determine that the persisted session state shouldnot be restored because, for example, the new session (i.e. the time ofcreation of the new session) was not initiated sufficiently proximate intime to a last updated time (similar to the last updated time 406 ofFIG. 4) of the persisted session state. In an implementation, thesession restoration module determines whether a persisted session stateis associated with a user of the client 104.

In an implementation, sufficient proximity in time can be satisfied ifthe time difference between the last updated time and the time that thefirst request is received from the client does not substantially exceeda predetermined or dynamically set threshold value. In anotherembodiment, the sufficient proximity in time is only satisfied if thetime difference is below the threshold value. For example, the thresholdvalue may be set to the user session timeout value configured for anapplication node, such as the application node 114 of FIG. 1. If theuser session timeout value is set to 20 minutes, then the persistedsession state should be restored if the time difference does notsubstantially exceed 20 minutes. Other configurations of the timedifference are also available. For example, the threshold value canrange from milliseconds to a few minutes. If the session restorationmodule determines that the persisted session state should not berestored, then control passes to operation 514 which is furtherdescribed below.

If the session restoration module determines that the persisted sessionstate should be restored, then control passes to operation 508. Atoperation 508, a request categorizer (similar to the request categorizermodule 304 of FIG. 3) can be used to determine the category of therequest. If the request is determined to be a stateless request, then atoperation 506 the request is processed by the application node 114 and aresponse is returned to the client 104. The response details thecategorization of the request and can be or include, for example, HTMLcontent, XML content, JSON content, a redirection to another location,an error message or an error code, executable instructions, or acombination thereof. If the request is not a stateless request, then atoperation 510, the session restoration module determines whether therequest received is the first stateful request received from the client104 in the new session. If it is not the first stateful request, thencontrol passes to the operation 506 without restoring a persistedsession state. The session restoration module can update session stateinformation (similar to the session state 404 in entry 410 of FIG. 4assuming that entry 410 is the persisted session state of the clientsession) to reflect session state changes maintained by the applicationnode 114.

If the session restoration module determines, at operation 510, that therequest is a first stateful request, then at operation 512, the sessionrestoration module determines whether a data structure (similar to thedata structure 400 of FIG. 4) contains a persisted session stateassociated with the client 104 by, for example, checking whether thedata structure contains an entry where a client ID (similar to theclient ID 402 of FIG. 4) is equal to the client device identifier of theclient 104. If the data structure contains a persisted session stateassociated with the client 104, control passes to operation 516,otherwise control passes to operation 514. At operation 516, the sessionrestoration module retrieves the persisted session state of the matchedentry in the data structure (e.g., retrieving the persisted sessionstate 404 of the matched entry 410 in the data structure 400 of FIG. 4)and associates the retrieved persisted session state with the clientsession identifier of the client 104. At operation 514, the sessionrestoration module creates a new entry in the data structure for the newsession. The session restoration module sets, in the new entry, a clientdevice identifier to a uniquely identifying value of the client 104, thepersisted session state (similar to the session state 404 entry), acurrent timestamp for the last updated time (similar to the last updatedtime 406 entry), and a session ID to the session identifier assigned by,e.g., the load balancer 110. Control then passes to operation 506 as thesystem awaits additional requests to process in accordance with thetechnique 500.

FIG. 6 is a flowchart illustrating an example of another technique 600for session restoration. The technique 600 can be executed usingcomputing devices, such as the systems, modules, and devices describedwith respect to FIGS. 1-4. The technique 600 can be performed, forexample, by executing a machine-readable program or othercomputer-executable instructions, such as instructions or programsdescribed according to JavaScript, C, or other such instructions. Thesteps, or operations, of the technique 600 or any other technique,method, process, or algorithm described in connection with theimplementations disclosed herein can be implemented directly inhardware, firmware, software executed by hardware, circuitry, or acombination thereof.

The technique 600 can include operations 602, 604, 606, 608, 610, and612. At operation 602, a first request that is a first type of requestis received from a new session of a client device. A new session meansthat there is not a tracked and on-going sequence of interactions withthe client device, from the point of view of the technique 600 or asystem in which it executes. At operation 604, the request is processedand a response is returned to the client device.

At operation 606, a second request is received and the technique 600determines that the second request is a first instance of a second typeof request received from in the new session. A “first instance of asecond type of request” means that prior requests of the second type ofrequest were not received in the new session but prior requests of thefirst type of request (such as the one from operation 602) could havebeen received. The second request (i.e. the first instance of the secondtype of request) may have been preceded by one or more of the first typeof requests. That is, zero or more first type, but no second type,requests may be received between the receiving of the first request(i.e. the first type of request) and the receiving of second request(i.e. the first instance of the second type of request). For example,five of the first type of requests can be received and are all referredto as the “first request” and, if the sixth received request is of thesecond type of request, then this sixth request is referred to as thesecond request (because it is the first instance of the second type ofrequest). In an implementation, the first type of request is a statelessrequest that does not use and/or change a session state of the clientdevice and the second type of request is a stateful request that doesuse and/or change the session state of the client device.

At operation 608, a determination is made whether to restore a persistedsession state. A determination is first made whether a persisted sessionstate associated with the client device exists, such as in a database. Asession state associated with the client device may be a persistedsession state associated with a user of the client device. In anotherembodiment, a session state associated with the client device may be apersisted session state associated with the client device itself. Atoperation 608, the determination whether a persisted session state is tobe restored can be carried out as described above with respect to theoperation 504 of FIG. 5. If it is determined that a persisted sessionstate is not to be restored, then the technique 600 ends at operation614.

At operation 610, if it is determined that the persisted session stateis to be restored, the technique 600 restores the persisted sessionstate for the client device from a data store, such as the datastructure 400 of FIG. 4. At operation 612, the persisted session stateis assigned as the session state of the new session of the clientdevice.

In an implementation, the methods and systems disclosed herein can beimplemented to transfer a client device's session from a firstapplication node to a second application node. In response to receivinga request from client device, a load balancer, such as the load balancer110 of FIG. 1, may determine that the first application node, assignedto the client device, is unavailable. For example, an application nodecan be unavailable when it experiences performance degradations, istaken offline, has unexpectedly shutdown, or any combination thereof.Other indications of unavailability are possible. When the firstapplication node is unavailable, the load balancer can forward a clientdevice's request to a second application node (or any other applicationnode of a plurality of application nodes that are available). The secondapplication node, upon receiving the client request, can perform or haveperformed the steps/operations of the techniques 500 and/or 600.

The methods and systems disclosed herein may be implemented in aone-node environment (e.g. an environment that may be non-clustered andnon-load balanced). For example, when an application node becomesunavailable it can lose a client device's session state when the sessionstate is maintained in the memory of the application node. The methodsdisclosed herein can be used to restore a client device's session stateto the application node when the client device makes a first new requestto the application node subsequent to the application node becomingavailable after a period of unavailability.

The methods and systems disclosed herein may be used to cause aspects ofa user's session state, not saved to a data structure, such as the datastructure 400 of FIG. 4, to be reset. For example, a session state for auser of a client, such as the client 104 of FIG. 1, may include a userpreference which can be, for example, a default system preference or auser defined preference. Such a user preference can be, for example,generated by an application node, such as the application node 114 ofFIG. 1, when a value for the preference is needed. A user preference canbe used to influence the operation of the web application. A setting fora user preference may, for example, cause performance degradation. Whensuch a preference is in a session state maintained by the applicationnode's session state, but is not in a subset session state saved to thedata structure, and when the user session is terminated in theapplication node, the user preference may be reset to a different valuewhen the user preference is recreated upon, for example, sessionrestoration. After the client 104's next request to the applicationnode, the session state can be restored by a session restoration module,such as the session restoration module 302 of FIG. 3. The restoredsession state can omit a given preference that causes performancedegradation because the persisted session state omits the givenpreference. Such a process may permit the removal of certain aspects ofsession state, while keeping more important aspects of session stateusing the session restoration system.

The session restoration module can restore, as a part of the sessionstate, data such as a cross-site request forgery (CSRF) token to permitthe web application to complete the processing of requests initiatedwith another application node. To the extent that the persisted sessionstate does not include information needed in the restored state, such asa CSRF token, the session restoration module can be configured to injectsuch data into the session state during the restoration process.

Furthermore, not all illustrated steps may be required to implement amethod in accordance with the disclosed subject matter. For example, thesession restoration module may save to and restore from the datastructure a session state for every stateful request received from theclient. As another example, session restore module may not performoperation 504 of FIG. 5.

Although the techniques 500 and 600 are shown as a series of operationsfor clarity, implementations of the techniques 500 and 600 or any othertechnique, process, or algorithm described in connection with theimplementations disclosed herein can be performed in various orders orconcurrently. Additionally, operations in accordance with thisdisclosure can be performed with other operations not presented anddescribed herein. Furthermore, one or more aspects of the systems andtechniques described herein can be omitted.

Another implementation of this disclosure is a system for restoring asession state of a client device. The system includes a means forreceiving a first request from the client device that is a first type ofrequest (e.g., a stateless request) and is associated with a new sessionof the client device, a means for processing the first request withoutpersisting a session state of the new session in the database node, ameans for receiving a second request from the client device that is afirst instance of a second type of request (e.g., a first statefulrequest) and is associated with the new session, and in responsedetermining to restore a persisted session state, a means for restoringthe persisted session state from the database node, and a means forassigning the persisted session state as the session state of the newsession of the client device.

All or a portion of the implementations of the systems and techniquesdescribed herein can be implemented using a general-purposecomputer/processor with a computer program that, when executed, carriesout any of the respective techniques, algorithms, or instructionsdescribed herein. In addition, or alternatively, for example, aspecial-purpose computer/processor can be utilized, which can includespecialized hardware for carrying out any of the techniques, algorithms,or instructions described herein.

The implementations of computing devices as described herein (and thealgorithms, techniques, instructions, etc., stored thereon or executedthereby) can be realized in hardware, software, or a combinationthereof. The hardware can include, for example, computers, intellectualproperty (IP) cores, application-specific integrated circuits (ASICs),programmable logic arrays, optical processors, programmable logiccontrollers, microcode, microcontrollers, servers, microprocessors,digital signal processors, or any other suitable circuit. In the claims,the term “processor” should be understood as encompassing any of theforegoing hardware, either singly or in combination.

For example, one or more computing devices can include an ASIC orprogrammable logic array (e.g., a field-programmable gate array (FPGA))configured as a special-purpose processor to perform one or more of theoperations described or claimed herein. An example FPGA can include acollection of logic blocks and random access memory (RAM) blocks thatcan be individually configured or configurably interconnected in orderto cause the FPGA to perform certain functions. Certain FPGAs cancontain other general- or special-purpose blocks as well. An exampleFPGA can be programmed based on a hardware definition language (HDL)design, such as VHSIC Hardware Description Language or Verilog.

The implementations disclosed herein can be described in terms offunctional block components and various processing operations. Suchfunctional block components can be realized by any number of hardware orsoftware components that perform the specified functions. For example,the described implementations can employ various integrated circuitcomponents (e.g., memory elements, processing elements, logic elements,look-up tables, and the like), which can carry out a variety offunctions under the control of one or more microprocessors or othercontrol devices. Similarly, where the elements of the describedimplementations are implemented using software programming or softwareelements, the systems and techniques can be implemented with anyprogramming or scripting language, such as C, C++, Java, assembler, orthe like, with the various algorithms being implemented with acombination of data structures, objects, processes, routines, or otherprogramming elements. Functional aspects can be implemented inalgorithms that execute on one or more processors. Furthermore, theimplementations of the systems and techniques could employ any number ofconventional techniques for electronics configuration, signal processingor control, data processing, and the like. The words “mechanism” and“element” are used broadly and are not limited to mechanical or physicalimplementations, but can include software routines in conjunction withprocessors, etc.

Likewise, the terms “module” or “monitor” as used herein and in thefigures may be understood as corresponding to a functional unitimplemented using software, hardware (e.g., an ASIC), or a combinationof software and hardware. In certain contexts, such modules or monitorsmay be understood to be a processor-implemented software module orsoftware-implemented monitor that is part of or callable by anexecutable program, which may itself be wholly or partly composed ofsuch linked modules or monitors.

Implementations or portions of implementations of the above disclosurecan take the form of a computer program product accessible from, forexample, a computer-usable or computer-readable medium. Acomputer-usable or computer-readable medium can be any device that can,for example, tangibly contain, store, communicate, or transport aprogram or data structure for use by or in connection with anyprocessor. The medium can be, for example, an electronic, magnetic,optical, electromagnetic, or semiconductor device. Other suitablemediums are also available. Such computer-usable or computer-readablemedia can be referred to as non-transitory memory or media, and caninclude RAM or other volatile memory or storage devices that can changeover time. A memory of an apparatus described herein, unless otherwisespecified, does not have to be physically contained by the apparatus,but is one that can be accessed remotely by the apparatus, and does nothave to be contiguous with other memory that might be physicallycontained by the apparatus.

The word “example” is used herein to mean serving as an example,instance, or illustration. Any aspect or design described herein as“example” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, the use of the word“example” is intended to present concepts in a concrete fashion. The useof any and all examples, or language suggesting that an example is beingdescribed (e.g., “such as”), provided herein is intended merely tobetter illuminate the systems and techniques and does not pose alimitation on the scope of the systems and techniques unless otherwiseclaimed. As used in this disclosure, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or.” That is, unlessspecified otherwise or clearly indicated otherwise by the context, thestatement “X includes A or B” is intended to mean any of the naturalinclusive permutations thereof. For example, if X includes A; X includesB; or X includes both A and B, then “X includes A or B” is satisfiedunder any of the foregoing instances. In addition, the articles “a” and“an” as used in this disclosure and the appended claims should generallybe construed to mean “one or more,” unless specified otherwise orclearly indicated by the context to be directed to a singular form.Moreover, use of the term “an implementation” or the term “oneimplementation” throughout this disclosure is not intended to mean thesame implementation unless described as such.

The particular implementations shown and described herein areillustrative examples of the systems and techniques and are not intendedto otherwise limit the scope of the systems and techniques in any way.For the sake of brevity, conventional electronics, control systems,software development, and other functional aspects of the systems (andcomponents of the individual operating components of the systems) cannotbe described in detail. Furthermore, the connecting lines, orconnectors, shown in the various figures presented are intended torepresent example functional relationships or physical or logicalcouplings between the various elements. Many alternative or additionalfunctional relationships, physical connections, or logical connectionscan be present in a practical device. Moreover, no item or component isessential to the practice of the systems and techniques unless theelement is specifically described as “essential” or “critical.”

The use of the terms “including,” “comprising,” “having,” or variationsthereof herein is meant to encompass the items listed thereafter andequivalents thereof as well as additional items. Unless specified orlimited otherwise, the terms “mounted,” “connected,” “supported,”“coupled,” or variations thereof are used broadly and encompass bothdirect and indirect mountings, connections, supports, and couplings.Further, “connected” and “coupled” are not restricted to physical ormechanical connections or couplings.

Unless otherwise indicated herein, the recitation of ranges of valuesherein is intended merely to serve as a shorthand alternative toreferring individually to respective separate values falling within therange, and respective separate values are incorporated into thespecification as if individually recited herein. Finally, the operationsof all techniques described herein are performable in any suitable orderunless clearly indicated otherwise by the context.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if respective references were individually and specificallyindicated as being incorporated by reference and were set forth in itsentirety herein.

The above-described implementations have been described in order tofacilitate easy understanding of the present systems and techniques, andsuch descriptions of such implementations do not limit the presentsystems and techniques. To the contrary, the present systems andtechniques are intended to cover various modifications and equivalentarrangements included within the scope of the appended claims, whichscope is to be accorded the broadest interpretation as is permitted bylaw so as to encompass all such modifications and equivalentarrangements.

The techniques presented and claimed herein are referenced and appliedto material objects and concrete examples of a practical nature thatdemonstrably improve the present technical field and, as such, are notabstract, intangible or purely theoretical. Further, if any claimsappended to the end of this specification contain one or more elementsdesignated as “means for [perform]ing [a function]. . .” or “step for[perform]ing [a function]. . .”, it is intended that such elements areto be interpreted under 35 U.S.C. 112(f). However, for any claimscontaining elements designated in any other manner, it is intended thatsuch elements are not to be interpreted under 35 U.S.C. 112(f).

1-20. (canceled)
 21. A system, comprising: a first server including aprocessor and a memory, accessible by the processor, the memory storinginstructions, that when executed by the processor, cause the processorsto perform operations comprising: receiving a request associated with acurrent session from a client device after a second server associatedwith a previous session experienced a failover condition; determiningthat the request is a first stateful request received from the clientdevice after the second server experienced a failover condition; andassigning a session state of the previous session to a session state ofthe current session.
 22. The system of claim 21, wherein assigning thesession state of the previous session to the session state of thecurrent session comprises restoring the session state of the previoussession from a database as the session state of the current session. 23.The system of claim 21, wherein assigning the session state of theprevious session to the session state of the current session comprisesassigning the session state of the previous session to the session stateof the current session in response to determining that the session stateof the previous session was last updated within a user session time outvalue of a time of creation of the current session.
 24. The system ofclaim 21, wherein the operations comprise: receiving a second requestassociated with the current session from the client device after thesecond server associated with the previous session experienced afailover condition; determining that the second request is a statelessrequest; and processing the stateless request without assigning thesession state of the previous session to the session state of thecurrent session.
 25. The system of claim 24, wherein the second requestassociated with the current session is received by the first applicationnode before the request associated with the current session.
 26. Thesystem of claim 21, comprising a load balancer configured to: receivethe request associated with the current session from the client device;determine that the second server associated with the previous sessionexperienced the failover condition; and forward the request associatedwith the current session to the first server.
 27. The system of claim21, wherein the operations comprise: receiving a second requestassociated with the current session from the client device after thesecond server associated with the previous session experienced afailover condition; determining that the second request is a secondstateful request received from the client device after the second serverexperienced a failover condition; and processing the second statefulrequest without assigning the session state of the previous session tothe session state of the current session.
 28. A method, comprising:receiving, at a first application node, a request associated with a newsession from a client device after a period of unavailability of asecond application node associated with a previous session of the clientdevice; determining, at the first application node, that the request isa first stateful request received from the client device after theperiod of unavailability of the second application node; and assigning,at the first application node, a session state of the previous sessionto a session state of the new session.
 29. The method of claim 28,wherein assigning the session state of the previous session to thesession state of the new session comprises restoring, at the firstapplication node, the session state of the previous session from adatabase as the session state of the new session.
 30. The method ofclaim 28, wherein assigning the session state of the previous session tothe session state of the new session comprises assigning the sessionstate of the previous session to the session state of the new session inresponse to determining that the session state of the previous sessionwas last updated within a user session time out value of a time ofcreation of the new session.
 31. The method of claim 28, comprising:receiving, at the first application node, a second request associatedwith the new session from the client device after the period ofunavailability of the second application node associated with theprevious session of the client device; determining, at the firstapplication node, that the second request is a stateless request; andprocessing, at the first application node, the stateless request withoutassigning the session state of the previous session to the session stateof the new session.
 32. The method of claim 31, wherein the secondrequest associated with the new session is received by the firstapplication node before the request associated with the new session. 33.The method of claim 28, comprising: determining, by a load balancer,that the second application node is unavailable; and forwarding, by theload balancer, the request associated with the new session to the firstapplication node.
 34. The method of claim 28, comprising: receiving, atthe first application node, a second request associated with the newsession from the client device after the period of unavailability of thesecond application node associated with the previous session of theclient device; determining, at the first application node, that thesecond request is a second stateful request received from the clientdevice after the period of unavailability of the second applicationnode; and processing, at the first application node, the second statefulrequest without assigning the session state of the previous session tothe session state of the new session.
 35. A non-transitory,computer-readable medium, comprising instructions that when executed byone or more processors, cause the one or more processors to performoperations comprising: receiving a request associated with a new sessionfrom a client device after a period of unavailability of an applicationnode associated with a previous session of the client device;determining that the request is a first stateful request received fromthe client device after the period of unavailability of the applicationnode; and assigning a session state of the previous session to a sessionstate of the new session.
 36. The non-transitory, computer-readablemedium of claim 35, wherein assigning the session state of the previoussession to the session state of the new session comprises restoring thesession state of the previous session from a database as the sessionstate of the new session.
 37. The non-transitory, computer-readablemedium of claim 35, wherein assigning the session state of the previoussession to the session state of the new session comprises assigning thesession state of the previous session to the session state of the newsession in response to determining that the session state of theprevious session was last updated within a user session time out valueof a time of creation of the new session.
 38. The non-transitory,computer-readable medium of claim 35, wherein the operations comprise:receiving a second request associated with the new session from theclient device after the period of unavailability of the application nodeassociated with the previous session of the client device; determiningthat the second request is a stateless request; and processing thestateless request without assigning the session state of the previoussession to the session state of the new session.
 39. The non-transitory,computer-readable medium of claim 38, wherein the second requestassociated with the new session is received before the requestassociated with the new session.
 40. The non-transitory,computer-readable medium of claim 35, wherein the instructions comprise:receiving a second request associated with the new session from theclient device after the period of unavailability of the application nodeassociated with the previous session of the client device; determiningthat the second request is a second stateful request received from theclient device after the period of unavailability of the applicationnode; and processing the second stateful request without assigning thesession state of the previous session to the session state of the newsession.